Click Here!
home account info subscribe login search My ITKnowledge FAQ/help site map contact us


 
Brief Full
 Advanced
      Search
 Search Tips
To access the contents, click the chapter and section titles.

Wireless Networking Handbook
(Publisher: Macmillan Computer Publishing)
Author(s): Jim Geier
ISBN: 156205631x
Publication Date: 09/01/96

Bookmark It

Search this book:
 
Previous Table of Contents Next


American Hytech’s NetGuru Simulator

American Hytech’s NetGuru Simulator is a fully functional network simulation module that is integrated with NetGuru Designer. The Simulator uses Object Oriented Programming techniques with graphical icons that enable even nontechnical users to perform design and simulation activities. The NetGuru family of tools have plug-and-play Microsoft Windows-based modules that represent generic physical and logical network elements. The product addresses the needs of professionals dealing with LANs and hundreds of workstations, or larger networks that can be further segmented.

NetGuru provides the ability to design the network from scratch or document an existing design and conduct a “what if” analysis. This helps the designer understand whether the networks are performing efficiently, identify potential bottlenecks, and predict the effect of new hardware, software, users, network configurations, or network tools as they relate to overall performance.

Verifying the Design through Design Reviews

Whether you have performed simulation and physical prototyping or not, you should conduct a design review as a final verification process. This review ensures there are no design defects or issues before pressing on with component procurements. It is best to have the entire team, especially analysts and engineers, review the design to ensure that it will adequately support all requirements. Analysts should raise questions related to the ability of the design to satisfy requirements, and engineers should be able to fully explain how the design will meet requirements. For first-time complex implementations, consider hiring a consultant to verify the design. This could eliminate many problems when installing and testing the system.

During the design review, participants should:

1.  Review all design documentation.
2.  Identify defects in the design.
3.  Describe potential technical problems.
4.  Recommend further prototyping or simulation of unclear design specifications.

Be sure to use lessons learned from other projects to spot problems in the inability of the specifications to meet requirements.

Documenting the Final Design

As with requirements, you need to document the details of the design to support further implementation activities, such as component procurements, installation, and so forth. Final design documentation should include the following:

  A description of each network element
  The location of access points
  Standards
  The products necessary for satisfying specific requirements


TIP:  

Be certain to update any documentation prepared throughout the design with any changes made after verifying the design. Also, update the project documentation, such as the budget, schedule, and resources required to complete the project.


The last step before procuring the components is to obtain approvals for the design. This ensures that applicable managers agree to fund the implementation shown in the design. Those involved usually include network configuration management, the customer representative, and people with funding authority. For approvals, you can have these people sign a letter with at least the elements shown in figure 8.14. After the approval, consider the design as a baseline that can only be changed by following the stated change control procedures.


Figure 8.14  The major elements of an approval letter.

Procuring Components

When procuring components, you need to understand the warranties and maintenance agreements vendors offer. Most vendors offer excellent warranties and also have maintenance agreements at an additional charge.

You should ask vendors the following questions:

  How long is the product covered?
  What are the limitations of the coverage?
  How should the product be returned if it becomes defective?
  Does the vendor provide on- or off-site maintenance?

Before ordering the components, you should plan where the components will be stored after delivery. For small implementations, this may not be significant, but for larger implementations, it is crucial. For example, imagine ordering 75 PCs, 150 network interface boards, and 5 printers. Do you know where to put all the boxes when they arrive? Because implementations of this size or larger require a great deal of space to store components before they are needed for installation, plan the following items:

  The location to which the components will be delivered.
  Storage locations for components waiting for installation.
  The mechanisms for moving components from the delivery point to the storage area.
  The mechanisms for moving the components from the storage area to the point of installation.


Previous Table of Contents Next


Products |  Contact Us |  About Us |  Privacy  |  Ad Info  |  Home

Use of this site is subject to certain Terms & Conditions, Copyright © 1996-2000 EarthWeb Inc.
All rights reserved. Reproduction whole or in part in any form or medium without express written permission of EarthWeb is prohibited. Read EarthWeb's privacy statement.